Overview

PR adds a new CI workflow: Run Tests Against Local Kava Network, which is run on every rosetta-kava commit. In the future it will be run on every kava commit as well.

A new CI workflow is based on already existing CI workflow: https://github.com/Kava-Labs/rosetta-kava/blob/master/.github/workflows/ci.yml. Main difference that new CI workflow is fully automated and run against local kava network, while old workflow requires manual intervention and run against testnet or mainnet.

New workflow consists of the following steps:

• run kava node with kvtool
• run two instances of rosetta-kava, one in online mode, another in offline mode
• execute integration tests
• execute check:construction
• execute check:data

NOTE: all tests are executed against local kava-node

Implementation details

Configuration files

PR adds a new folder rosetta-cli-conf/kava-localnet-ci which was created based on rosetta-cli-conf/kava-testnet-ci.

Main changes are:

• removing of cache directory, all tests are run from scratch every time, we don't need start where it last left off functionality
• using of different ports for online and offline URLs
• using of another predefined account, new predefined account is a kvtool whale account

Scripts

PR adds a new folder .github/scripts/kava-localnet-ci, which contains 3 scripts:

• setup.sh - starts 2 instances of rosetta-kava
• construction.sh- runs check:construction
• cli.sh - runs check:data

Newly added scripts are based on already existing ones: https://github.com/Kava-Labs/rosetta-kava/tree/master/.github/scripts and modified to work with local kava network.

Questions

1. for check:data we run it against latest 10 blocks, should we adjust this number?
2. I think mostly these blocks are empty, should we simulate some load, some transactions?

Follow-up PRs:

• Use specific kava & rosetta versions #70
• ci: dispatch run-rosetta-tests event to rosetta-kava kava#2007
• Send slack notification if CI failed #71